Single point of contact personal communication system

ABSTRACT

A computer/telephony integrated single-point-of-contact system (CISS) enabling a user to contact another using multiple devices with a single contact attempt is disclosed. A plurality of computer programs residing in a computer use a subscriber database, authorization database, priority list database, and device attributes database to determine how to respond to a request to contact a subscriber. If the request is an emergency, the computer repeatedly contacts all of the subscriber&#39;s devices until a response is received. Otherwise, the computer contacts the subscriber&#39;s devices in a sequential order determined by the subscriber. The computer can also delete redundant un-received messages from a subscriber&#39;s devices and create a real-time connection between the requester and the subscriber, if it is technically possible, at the subscriber&#39;s request.

FIELD OF THE INVENTION

The present invention relates to communication systems in general, and in particular to a system for one individual to contact another using multiple devices with a single contact attempt.

BACKGROUND OF THE INVENTION

Single point of contact personal communication systems are desirable for providing a way for one individual to contact another using multiple devices with a single contact attempt. Many individuals use multiple devices and methods to stay in contact with others. Unfortunately, it can be difficult for a person seeking to contact an individual who uses multiple devices and methods for communication because it is unclear what is the best method or device to use. In addition, the requester may not have access to the contact information for all of the individual's devices. Time can be wasted trying multiple methods or trying to locate unknown contact information for the devices, and the person being contacted can wind up with multiple redundant messages on their devices that have to be addressed. Speed in contacting a person is particularly important in the case of an emergency, but the plethora of devices and methods that are designed to make it possible to contact someone in a broad range of circumstances can instead create confusion and delays.

The use of personal emergency, safety warning systems and methods is known in the prior art. For example, U.S. Pat. No. 6,028,514 to Lemelson et al. (the '514 patent) discloses a personal emergency, safety warning system and method. However, the '514 patent does not actively seek contact with any specific individual, and has further drawbacks of requiring an individual to have a specialized receiver.

U.S. Pat. No. 6,728,341 to Puchek et al. (the '341 patent) discloses a monitoring and communication system for stationary and mobile persons that monitors a supervised person. However, the '341 patent does not contact an individual using multiple devices in a sequence defined by that individual, and additionally does not allow the monitored individual to delete redundant inquiries from multiple devices.

Similarly, United States Patent Application Publication No. 2002/0184346 to Mani (the '346 published application) discloses an emergency notification and override service in a multimedia-capable network that effectuates a subscriber-selectable notification scheme with respect to an incoming emergency message directed to a subscriber from an authorized entity. However, the '346 published application publication does not allow an individual to be contacted with non-emergency messages, and does not use the expiration of an allotted time to denote message delivery failure.

In addition, United States Patent Application Publication No. 2003/0069002 to Hunter et al. (the '002 published application) discloses a system and method for emergency notification content delivery that disseminates emergency notification content from an emergency originating source. However, the '002 published application does not connect the transmitting party to the user for real-time communication upon request of the user after verifying that the user's device supports real-time communication with the transmitting party, and also does not notify users of nonemergency messages.

Lastly, United States Patent Application Publication No. 2004/0096042 to Orwick et al. (the '042 published application) discloses an emergency telephone call notification service system and method that provides emergency telephone call notification. However, the '042 published application does not actively attempt to notify a specific individual, and further lacks the ability to contact devices other than telephones.

A need exists for a single point of contact personal communication system that can be used to initiate contact attempts on multiple devices when a user makes a single attempt on one device.

SUMMARY OF THE INVENTION

The invention that meets the need described above is a computer/telephony integrated single-point-of-contact system (CISS) that allows a person to initiate multiple attempts to reach a subscriber on multiple devices by only making a single attempt to contact that subscriber on one device. CISS comprises a computer linked to a plurality of databases, a telephone interface attached to the computer, an Internet interface attached to the computer, and a plurality of computer programs in memory or storage connected to the computer. The plurality of databases include device an attributes database, a subscriber database, an authorization database, a device status database, and a message status database. The computer programs determine how to respond to a request to contact a subscriber. If the request is an emergency, the computer repeatedly contacts all of the subscriber's devices until a response is received. Otherwise, the computer contacts the subscriber's devices in a sequential order determined by the subscriber. The computer can also delete redundant un-received messages from a subscriber's devices and create a real-time connection between the requester and the subscriber, if it is technically possible, at the subscriber's request.

The subscriber database stores contact information about individuals. The authorization database stores information about who is authorized to contact a particular subscriber. The device attributes database stores contact information for each subscriber device, along with a time interval to wait before contacting the next device if the subscriber does not respond. The priority list database stores information about the order in which a subscriber's devices are to be contacted. The device status database stores information regarding whether the device is operational as well as its user's status. The message status database stores information regarding the delivery and receipt of messages. When a user makes a call on one device, a computer program searches the subscriber database and finds a plurality of corresponding records in the device attributes database and uses the telephone interface and the Internet interface to send a message to a plurality of devices.

CISS allows an individual to configure a system so that all of their devices can be contacted at once or contacted in a desired sequence in response to a single request for contact. Furthermore, CISS allows users to optionally delete redundant messages from their devices and to initiate real-time communication with the requester if it is technically feasible. CISS allows the individual being contacted to give out only one method for contacting the individual while still allowing the request for contact to be received on any of their devices. Thus CISS allows the individual to gain the convenience of being contacted on any of their devices while maintaining privacy in terms of what types of devices they have and how the individual can be reached directly.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will be understood best by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 is a schematic of the computer/telephone integrated single-point-of-contact system (CISS) in an enterprise environment;

FIG. 2 is a schematic of the computer/telephone integrated single-point-of-contact system in an integrated communications supplier environment;

FIG. 3 is a flow diagram of the process for configuring the authorization database, device attributes database, priority list database, and subscriber database;

FIG. 4 a is a flow diagram of the process for contacting an individual using the single point of contact personal communication system;

FIG. 4 b is a flow diagram of the process for contacting an individual using the single point of contact personal communication system;

FIG. 4 c is a flow diagram of the process for contacting an individual using the single point of contact personal communication system;

FIG. 5 is a flow diagram of the process for converting the user's message to a format that is compatible with the individual's devices;

FIG. 6 a is a schematic of the priority list database;

FIG. 6 b is a schematic of an alternative embodiment of the priority list database;

FIG. 7 is a schematic of the device attributes database;

FIG. 8 is a schematic of the authorization database;

FIG. 9 is a schematic of the subscriber database;

FIG. 10 is a schematic of the device status database; and

FIG. 11 is a schematic of the message status database.

DESCRIPTION OF THE PREFERRED EMBODIMENT

The principles of the present invention are applicable to a variety of computer hardware and software configurations. The term “computer hardware” or “hardware,” as used herein, refers to any machine or apparatus that is capable of accepting, performing logic operations on, storing, or displaying data, and includes without limitation processors and memory; the term “computer software” or “software,” refers to any set of instructions operable to cause computer hardware to perform an operation. A “computer,” as that term is used herein, includes without limitation any useful combination of hardware and software, and a “computer program” or “program” includes without limitation any software operable to cause computer hardware to accept, perform logic operations on, store, or display data. A computer program may, and often is, comprised of a plurality of smaller programming units, including without limitation subroutines, modules, functions, methods, and procedures. Thus, the functions of the present invention may be distributed among a plurality of computers and computer programs. The invention is described best, though, as a single computer program that configures and enables one or more general-purpose computers to implement the novel aspects of the invention.

FIG. 1 illustrates computer/telephony integrated single-point-of-contact system (CISS) 104 installed in enterprise 102 (hereafter referred to collectively as “the first system”). Enterprise 102 is a business, such as a corporation, which is oriented towards facilitating contact with the employees of enterprise 102. CISS 104 has computer 105 connected to priority list database 600, device attributes database 700, authorization database 800, subscriber database 900, device status database 1000 and message status database 1100. Computer 105 is the central management server for CISS 104. Subscriber database 900 stores information about individuals first system 100 can contact. Authorization database 800 stores information about who is authorized to use first system 100 to contact a particular subscriber. Device attributes database 700 stores contact information for each subscriber device 620 (as shown in FIG. 6A and FIG. 6B), along with a time interval to wait before contacting the next subscriber device 620 if the subscriber does not respond. Priority list database 600 stores information about the order in which a subscriber's devices 620 are to be contacted.

CISS 104 has telephone interface 110 and Internet interface 112 so that it can contact telephonic and text-based devices 620. For contacting devices 620 contained within enterprise 102, telephone interface 110 is connected to telephony switch 114, such as a Private Branch Exchange, and Internet interface 112 is connected to corporate intranet 116. Telephony switch 114 provides first system 100 with access to devices 620 such as office phones 118, facsimile machines 122, and voicemail system 124 within enterprise 102. Corporate intranet 116 provides access to personal computers 120, e-mail server 126 and Instant Messaging (IM) server 127 located within enterprise 102. From telephony switch 114 and corporate intranet 116, system 100 can also access devices 620 outside of enterprise 102. Telephony switch 114 is connected to telephone central office 128. Telephone central office 128 enables first system 100 to contact cellular phones 140 through cellular phone service providers 134, wireless Personal Digital Assistants (PDAs) 146 through wireless PDA service providers 144, pagers 150 through paging service providers 148, facsimile machines 142, telephones 138, and other telephone-based services 132.

Corporate intranet 116 is connected to Internet 130. Internet 130 provides first system 100 with access to cellular phones 140 through cellular phone service providers 134, wireless PDAs 146 through wireless PDA service providers 144, pagers 150 through paging service providers 148, personal computers 120, and other computer-based services 136. Through these connections, first system 100 can contact devices 620 with voice messages, text messages, or both depending upon the capabilities of devices 620 and how the subscriber has configured device attributes database 700. The subscriber does not have to reveal any information to the requester about the nature of their devices 620 other than how to contact first system 100, and first system 100 can initiate a real-time connection between the requester and the subscriber at the subscriber's request if it is technically feasible.

FIG. 2 depicts CISS 104 installed in integrated communications supplier 202 (hereafter referred to collectively as “the second system”). Integrated communications supplier 202 is a business oriented towards providing services to third parties, including consumers and small companies. In this example, integrated communications supplier 202 is a utility that acts as paging service provider 148, wireless PDA service provider 144, cellular phone service provider 134, cable television service provider 254, and Internet service provider 216. However, integrated communications supplier 202 need not supply all of these services itself, and may utilize connections to other integrated communications suppliers to provide services. CISS 104 has computer 105 connected to priority list database 600, device attributes database 700, authorization database 800, subscriber database 900, device status database 1000 and message status database 1100. Computer 105, subscriber database 900, authorization database 800, device attributes database 700, and priority list database 600 have the same purpose they have in first system 100 embodiment of the current invention. CISS 104 has telephone interface 110 and Internet interface 112 so that it can contact telephonic and text-based devices 620. Telephone interface 110 is connected to telephony switch 114, and Internet interface 112 is connected to Internet service provider 216. Telephony switch 114 provides system 200 with access to telephones 138, facsimile machines 142, personal computers 120, telephone central office 128, and other telephone-based services 132. A connection to cellular phone service providers 134 provides access to cellular phones 140. Internet service provider 216 provides a connection to e-mail server 126, instant messaging (IM) server 127, personal computers 120, and Internet 130. CISS 104 is also connected to pagers 150 through paging service providers 148, wireless PDAs 146 through Wireless PDA service providers 144, and television sets 256 through cable television service providers 254. Like first system 100, second system 200 can contact the subscriber using text or voice-based devices 620 and maintains the subscriber's privacy. Second system 200 can also establish a real-time connection between the subscriber and the requester if desired and technically feasible.

FIG. 3 depicts first program 300 for configuring the authorization database, device attributes database, priority list database, and subscriber database of the present invention. First program 300 begins when the subscriber contacts first system 100 or second system 200. If the subscriber wants to change their profile (305), first program 300 presents the subscriber with the opportunity to make changes to the subscriber's authorization list (310). If the subscriber answers affirmatively, first program 300 makes subscriber-directed changes to the authorization list (315). After the subscriber makes changes to the authorization list, or if no changes were desired, first program 300 gives the subscriber the opportunity to make changes to the subscriber's communication devices list (320). If the subscriber answers affirmatively, first program 300 makes subscriber-directed changes to the communication devices list (325). After the subscriber makes changes to their communication devices list, or if no changes were desired, first program asks if the subscriber wants to make any changes to the subscriber's priority lists or to create a new one (330). If the subscriber answers affirmatively, first program 300 adds a priority list or changes one in response to the subscriber's instructions (335). After the subscriber makes changes or adds a priority list, first program 300 asks if the subscriber wants to make any more changes to his or her priority lists (340). If the subscriber answers affirmatively, steps 330, 335, and 340 repeat until the user responds to step 340 in the negative. Once the subscriber has finished making changes to the subscriber's priority lists, or if no changes were desired, first program 300 presents the subscriber with the opportunity to change the subscriber's status, including which priority list is currently active (345). If the subscriber answers affirmatively, the system changes the subscriber's status (350) in response to instructions from the subscriber. Once any changes to the subscriber's status are made, or if no changes were desired, the first program 300 terminates.

FIGS. 4 a through 4 c depicts second program 400. Second program 400 begins when a requester attempts to communicate with a subscriber by contacting first system 100 or second system 200 by telephone (402) or by Internet (404). If the initial contact is by telephone, second program 400 monitors to see if the subscriber answers (406). If the subscriber answers, then the requester is permitted to talk to them (408), and second program 400 terminates. If the subscriber does not answer, the requester is given the opportunity to request that the subscriber be tracked down (410). If the requester responds negatively, then the requester can leave voicemail (412), and second program 400 terminates. If the requester responds affirmatively, or if the requester initiated contact by the Internet, second program 400 checks the authorization database (414) and determines if the requester is authorized (416). If the user is not authorized, then second program 400 terminates. If the requester is authorized, then second program 400 takes a message from the requester (418) and then inquires if the message regards an emergency (420). If it is an emergency, second program 400 attempts contact on all devices (422) and monitors first system 100 or second system 200 to determine if contact was achieved (424). If contact is not achieved, second program 400 tries contacting the subscriber again using appropriate devices (426). Second program 400 repeats steps (424) and (426) until contact is achieved.

If the situation is not an emergency, then second program 400 retrieves the active priority list (428) and attempts to contact the subscriber using the device at the top of the priority list (430). After waiting the amount of time specified in the device attributes database (432), second program 400 checks to see if contact was achieved (434). If contact was not achieved, second program 400 checks to see if all of the devices in the priority list have been tried (438). If they have not been tried, second program 400 again attempts contact using the next device in the priority list (436), and to repeat steps (432), (434), (438), and (436) until step (438) indicates that all devices in the priority list have been tried. Once all devices have been tried, second program 400 restarts at the top of the priority list (440) and resumes repeating steps (432), (434), (438), (436) and, when applicable, (440) until contact is achieved. Once contact is achieved, regardless of whether the situation is an emergency or not, second program 400 notifies the requester of message delivery (442) and gives the contacted subscriber the option of deleting previous contact attempts (444). If the subscriber answers affirmatively, second program 400 deletes previous un-received contact attempts from all devices (446).

Once the previous contact attempts have been deleted, or if the contacted subscriber did not want to delete the previous contact attempts, second program 400 determines if the requester is still holding (448). If the requester is not holding, then second program 400 terminates. If the requester is holding, second program 400 checks to see if the requester's device and the contacted subscriber's device are capable of real-time communication (450). If this is not the case, then second program 400 terminates. Otherwise, second program 400 asks the contacted subscriber if they wish to be connected to the requester (452). If the response is negative, second program 400 terminates. Otherwise, second program 400 connects the contacted subscriber to the requester (454), and then second program 400 terminates.

FIG. 5 depicts third program 500. Third program 500 is invoked during steps (422), (426), (430), and (436) of second program 400 to ensure that the requester's message is in a form that can be received by the device that second program 400 is attempting to contact. Third program 500 first determines if the requester's message is text (502). If the message is text, then third program 500 checks device attributes database 700 to determine if the subscriber's device can receive text (504). If the subscriber's device can receive text, then third program 500 sends the text message to the subscriber's device (512), and third program 500 terminates. If the subscriber's device cannot receive text, then third program 500 converts the text message to an audio message (506). Conversion of the text message to an audio message may be accomplished using known speech synthesis software. Third program 500 then sends the resulting audio message to the subscriber's device (512), and third program 500 terminates. If the requester's message is not text, third program 500 checks device attributes database 700 to determine if the subscriber's device can receive audio (508). If the subscriber's device can receive audio, then third program 500 sends the audio message to the subscriber's device (512), and third program 500 terminates. If the subscriber's device cannot receive audio, then third program 500 converts the audio message to a text message (510). Conversion of the audio message to a text message may be accomplished using known speech recognition software. Third program 500 then sends the resulting text message to the subscriber's device (512), and third program 500 terminates. Third program 500 works in the same manner if a requester's message is audio. The words “text” and “audio” may be exchanged in FIG. 5 to depict the operation of third program 500 when the requester's message is audio.

FIG. 6 a depicts priority list database 600. Priority list database 600 has one or more priority list records 600 containing subscriber key 605, priority list name 610, priority list ID number 615, and a listing of one or more devices 620. In the preferred embodiment, priority list 600 contains devices 620 used to contact the subscriber in the order they are used. Subscriber key 605 is used to index records in priority list database 600, device attributes database 700, authorization database 800, and subscriber database 900. Priority list name 610 and priority list ID number 615 allow each subscriber to maintain and manage a plurality of priority list records in priority list database 600 if desired.

FIG. 6 b depicts alternate priority list database 635 having the same priority list records as priority list database 630 but also having an order number 625 for each device 620. In this embodiment, priority list 635 stores devices 620 in no particular order, and order number 625 for each device 620 is used to determine the order of usage of devices 620 for contacting the subscriber.

FIG. 7 depicts device attributes database 700 having one more records containing subscriber key 605, devices 620, service type 705, repeat flag 710, response wait time 715, and other device attributes 720. Device attributes database 700 provides CISS 104 with information about how to interact with subscriber's devices 620. Service type 705 and other device attributes 720 tell CISS 104 what types of messages each device 620 can receive, how to contact the device 620, and whether or not device 620 is capable of real-time communication using one or more message types. Repeat flag 710 indicates whether or not repeated attempts should be made to contact the subscriber using this device 620. For example, calling a cellular phone again may be appropriate, but sending an additional e-mail would be redundant. Response wait time 715 tells CISS 104 how long to wait before contacting the next device in priority list 600 or alternate priority list 635. In the case of an emergency situation, CISS 104 will ignore priority list 600 or alternate priority list 635, repeat flag 710, and response wait time 715 and immediately contact all devices 620 and continue doing so at subscriber-defined intervals until a response from the subscriber is received.

FIG. 8 depicts authorization database 800 having subscriber key 605, authorized user name 805, authorized user ID 810, and authorized user password 815. Authorization database 800 is used by the subscriber to maintain a list of authorized users who can use system 100 to contact them. Second program 400 matches the information supplied by the requester with authorized user ID 810 and authorized user password 815 before initiating contact attempts (see FIG. 4 a, steps 414 and 416). Authorization database 800 may also include information that assigns a particular priority list 600 to requests from a specific requester.

FIG. 9 depicts subscriber database 900 having subscriber key 605, subscriber name 905, subscriber user ID 910, subscriber password 915, active priority list 920, and other subscriber information 925. One example of other subscriber information would be election of an automatic cancellation option. By automatic cancellation option is meant a choice whereby a subscriber can activate instructions to CISS 102 that after a message has been delivered to one device, and after an answer has been received from the recipient of the delivered message, all attempts to deliver the same message to other devices will be cancelled. Another example of other subscriber information is that a subscriber can enter instructions to amend or alter priority and cancellation based upon subscriber entry of a subscriber status. Such a subscriber status could be that the subscriber is on vacation, or that the subscriber will be traveling for several days, and by entering a vacation or a travel status, any priority, delivery, and cancellation instructions can be amended or altered accordingly. Second program 400 matches information supplied by the subscriber with subscriber user ID 910 and subscriber password 915 before allowing the subscriber to initiate first program 300. Active priority list 920 determines the default priority list 600 or alternate priority list 635 that system 100 or system 200 should use in response to a contact request unless it is overridden by information in the authorization database 800.

FIG. 10 depicts device status database 1000 showing an array having message column 1020 and the following representative device columns: device 1 column, device 2 column 1040, device 3 column 1050 and device 4 column 1060. In the example, two subscriber keys are represented by A and B. Subscriber A has not activated automatic cancellation 930 in the subscriber database 900, while subscriber B has activated automatic cancellation 930. A subscriber can make such an election by adding such a desire to the subscriber database 900. Two messages have been sent to subscriber A. The status of message 1 can be seen in each device column. In this case, message 1 is pending for device 1 (meaning that delivery has not been completed), message 1 has been delivered to device 2, message 1 is pending for device 3 and also pending for device 4. For subscriber A, message 2 has been delivered to device 1 and device 2, and is pending for device 3 and 4. For subscriber B, message 1 has been delivered for device 1 and is pending for devices 2 through 4. For subscriber B, message 2 is delivered to device 1 and 2 and attempts to deliver message 2 to devices 3 and 4 have been cancelled. The cancellation occurred because subscriber B had activated automatic cancellation, and the message status for device 2 shows that the message was delivered and also that it was answered. Therefore, as soon as the message was answered, attempts to deliver the message to the remaining devices were cancelled by CISS 104.

FIG. 11 depicts device status database 1100 showing an array having a subscriber key column 1110, a device column 1120, a subscriber status column 1130, a poll status 1140 and an instruction pointer 1150. In the example shown, subscriber A has four devices. CISS 104 has polled the devices in the system to determine whether they are accessible or not, and the status of each device is shown as either “on” or “off.” Subscriber A has entered a vacation status for device 2. Instruction pointer 1150 contains pointers to an array of instructions (not shown) to alter or amend the priority, delivery, and cancellation instructions for subscriber A based upon the device status. Subscriber B has entered a “vacation” status for device 3 and a “travel” status for device 4. The CISS 104 poll of devices shows that device 3 and device 4 are off. CISS 104 will follow instructions based upon the instruction pointers activated by the subscriber status and the poll status for subscriber B.

While a current embodiment of the single point of contact personal communication system has been described in detail, it should be apparent that modifications and variations thereto are possible, all of which fall within the true spirit and scope of the invention. Therefore, the foregoing is considered as illustrative only of the principles of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation shown and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope of the invention. 

1. A single point of contact personal communication system comprising: a device attributes database; a subscriber database; a computer linked to the device attributes database and the subscriber database; a telephone interface attached to the computer; an Internet interface attached to the computer; and a computer program residing within the computer, wherein responsive to a request to contact an individual from a user received via at least one of the telephone interface and the Internet interface, the computer program searches the subscriber database and, responsive to finding a record matching the individual, finds a corresponding record in the device attributes database and uses at least one of the telephone interface and the Internet interface to send a message to at least one device in a list of devices found in the record in the device attributes database.
 2. The system of claim 1, further comprising an authorization database, wherein the computer, prior to locating a corresponding record in the device attributes database, verifies that the user is authorized to contact the individual using the system by first locating a record matching the user in the authorization database.
 3. The system of claim 1, further comprising a priority list database, wherein the computer program locates a corresponding record in the priority list database to determine the order and locates a corresponding record in the device attributes database to determine the timing in which the message is sent to at least one device in the list of devices.
 4. The system of claim 1, further comprising a telephone system connected to the telephone interface.
 5. The system of claim 4, wherein the telephone system is at least one of the group consisting of a Private Branch Exchange, a Private Automatic Branch Exchange, and a Computerized Branch Exchange.
 6. The system of claim 5, wherein the telephone system is connected to at least one of the group consisting of office phones, facsimile machines, voicemail systems, and a telephone central office.
 7. The system of claim 6, wherein the telephone central office is connected to at least one of the group consisting of telephones, facsimile machines, paging service providers, wireless Personal Digital Assistant service providers, cellular-phone service providers, and other telephone-based services.
 8. The system of claim 1, further comprising a corporate intranet connected to the Internet interface.
 9. The system of claim 8, wherein the corporate intranet is connected to at least one of the group consisting of personal computers, e-mail servers, instant messaging servers, and the Internet.
 10. The system of claim 9, wherein the Internet is connected to at least one of the group consisting of cellular-phone service providers, wireless Personal Digital Assistant service providers, paging service providers, personal computers, instant messaging service providers, and other computer-based services.
 11. The system of claim 1, wherein responsive to input received via at least one of the telephone interface and the Internet interface from the individual, the computer program adds, deletes, and/or edits at least one of the records in the subscriber database and/or the records in the device attributes database.
 12. The system of claim 2, wherein responsive to input received via at least one of the telephone interface and the Internet interface from the individual, the computer program adds, deletes, and/or edits at least one of the records in the authorization database.
 13. The system of claim 3, wherein responsive to input received via at least one of the telephone interface and the Internet interface from the individual, the computer program adds, deletes, and/or edits at least one of the records in the priority list database.
 14. The system of claim 1, wherein responsive to instructions contained in the record in the device attributes database, the computer program converts the message into a format that is receivable by the device.
 15. The system of claim 14, wherein the computer program converts the format of the message using at least one of the group consisting of speech-recognition software and speech synthesis software.
 16. The system of claim 1, wherein responsive to a status of delivered and answered in a message status database, the computer cancels all remaining attempts to contact a subscriber.
 17. The system of claim 1, wherein responsive to a status entered by a subscriber in a device status database, the computer receives alternate instructions on the priority of attempts to contact the subscriber.
 18. A single point of contact personal communication system comprising: a device attributes database; a subscriber database; a computer linked to the device attributes database and the subscriber database; a telephone interface attached to the computer and connected to a telephone switch; an Internet interface attached to the computer and an Internet service provider; a cable-television interface connected to a cable-television service provider; and a computer program residing within the computer, wherein the computer program, responsive to a request to contact an individual from a user received via at least one of the telephone interface and the Internet interface, searches the subscriber database and, responsive to finding a record matching the individual, finds a corresponding record in the device attributes database and uses at least one of the telephone interface, the Internet interface, and the cable-television interface to send a first message to at least one device in a list of devices found in the record in the device attributes database.
 19. The system of claim 18, further comprising an authorization database, wherein the computer, prior to locating a corresponding record in the device attributes database, verifies that the user is authorized to contact the individual using the system by first locating a record matching the user in the authorization database.
 20. The system of claim 18, further comprising a priority list database, wherein the computer program locates a corresponding record in the priority list database to determine the order and locates a corresponding record in the device attributes database to determine the timing in which the first message is sent to at least one device in the list of devices.
 21. The system of claim 18, wherein the telephone switch is connected to at least one of the group consisting of paging service providers, wireless Personal Digital Assistant service providers, cellular-phone service providers, telephones, facsimile machines, personal computers, telephone central offices, voicemail, and other telephone-based services.
 22. The system of claim 18, wherein the Internet service provider is connected to at least one of the group consisting of e-mail servers, instant messaging servers, personal computers, and the Internet.
 23. The system of claim 18, wherein responsive to receiving a second message from the individual that the first message has been received, the computer program sends a third message to the user advising the user that the first message has been received by the individual.
 24. The system of claim 18, wherein responsive to a second message received from the individual that the first message has been received, the computer program sends a fourth message to all devices that did not send the second message commanding the devices to delete the first message.
 25. The system of claim 18, wherein responsive to finding the user and the individual are using devices capable of real-time communication with one another and responsive to receiving a message from the individual, the computer program directly connects the user to the individual.
 26. The system of claim 18, wherein responsive to a status of delivered and answered in a message status database, the computer cancels all remaining attempts to contact a subscriber.
 27. The system of claim 18, wherein responsive to a status entered by a subscriber in a device status database, the computer receives alternate instructions on the priority of attempts to contact the subscriber.
 28. A method for contacting an individual comprising the steps of: (a) receiving a request from a user to contact an individual; (b) responsive to finding that the request is a phone call, ringing the individual's telephone; (c) responsive to finding that the individual does not answer the telephone, giving the user a choice of leaving voicemail or tracking down the individual; (d) responsive to a request to track down the individual or finding that the request is text-based, checking an authorization database to verify the user is authorized to track down the individual; (e) responsive to finding that the user is authorized, taking a first message from the user for the individual; (f) sending a request to the user to indicate if the first message regards an emergency; (g) receiving a response from the user; (h) responsive to the response in step (g) indicating the first message regards an emergency, locating a record for the individual in a device attributes database; (i) responsive to the response in step (g) indicating the first message regards an emergency, sending the message to all devices in a list of devices in the record; (i) responsive to the response indicating the first message does not regard an emergency, locating a record for the individual in a priority list database and in a device attributes database and sending the first message to a first device in the record in the priority list database; (j) waiting a period specified in the record in the device attributes database; (k) responsive to the response in step (g) indicating the message regards an emergency, and in the absence of a second message from the individual, repeating steps (i) and (j) until a message is received from the individual; (l) responsive to the response in step (g) indicating the first message does not regard an emergency, and in the absence of receiving a second message from the individual, sending the first message to a subsequent device in the list of devices; (m) responsive to the response in step (g) indicating the first message does not regard an emergency, and in the absence of receiving a second message from the individual, repeating steps (j) and (l) until a second message is received from the individual or the first message has been sent to all devices; (n) responsive to the response in step (g) indicating the first message does not regard an emergency, in the absence of receiving a second message from the individual, and when the first message has been sent to all devices, repeating steps (i), (j), (l), (m), and (n).
 29. The method of claim 28, further comprising the step of sending a third message to the user that the first message has been received by the individual.
 30. The method of claim 28, further comprising the steps of: determining if the device sending the second message is capable of real-time communication with the user; responsive to finding that the device sending the second message is capable of real-time communication with the user, sending a request to the individual to indicate if the individual desires to be connected to the user; receiving a response from the individual; responsive to the response indicating the individual desires to be connected to the user, connecting the individual to the user.
 31. The method of claim 28, further comprising the steps of: sending a request to the individual to indicate if the individual desires to delete the first message from all devices not sending the second message; receiving a response from the individual; responsive to the response indicating the individual desires the first message to be deleted from all devices not sending the second message, deleting the first message from all devices not sending the second message.
 32. A method for configuring a single point of contact personal communication system comprising the steps of: (a) receiving a request from a user to configure the system; (b) checking a subscriber database to verify the user is authorized to configure the system; (c) responsive to finding that the user is authorized, sending a request to the user to indicate if the user wishes to change their profile; (d) receiving a response from the user; (e) responsive to the response in step (d) indicating the user wishes to change their profile, sending a request to the user to indicate if the user wishes to change their authorization list; (f) responsive to the response in step (d) indicating the user wishes to change their profile, receiving a response from the user; (g) responsive to the response in step (f) indicating the user wishes to change their authorization list, sending a request to the user to indicate the changes to their authorization list; (h) responsive to the response in step (f) indicating the user wishes to change their authorization list, receiving a response from the user; (i) responsive to the response in step (f) indicating the user wishes to change their authorization list, changing the authorization list of the user to match the response received in step (h); (j) responsive to the response in step (d) indicating the user wishes to change their profile, sending a request to the user to indicate if the user wishes to change their device attributes list; (k) responsive to the response in step (d) indicating the user wishes to change their profile, receiving a response from the user; (l) responsive to the response in step (k) indicating the user wishes to change their device attributes list, sending a request to the user to indicate the changes to their device attributes list; (m) responsive to the response in step (k) indicating the user wishes to change their device attributes list, receiving a response from the user; (n) responsive to the response in step (k) indicating the user wishes to change their device attributes list, changing the device attributes list of the user to match the response received in step (m); (o) responsive to the response in step (d) indicating the user wishes to change their profile, sending a request to the user to indicate if the user wishes to change their priority lists; (p) responsive to the response in step (d) indicating the user wishes to change their profile, receiving a response from the user; (q) responsive to the response in step (p) indicating the user wishes to change their priority lists, sending a request to the user to indicate the changes to their priority lists; (r) responsive to the response in step (p) indicating the user wishes to change their priority lists, receiving a response from the user; (s) responsive to the response in step (p) indicating the user wishes to change their priority lists, changing the priority lists of the user to match the response received in step (r); (t) sending a request to the user to indicate if the user wishes to change their status; (u) receiving a response from the user; (v) responsive to the response in step (u) indicating the user wishes to change their status, sending a request to the user to indicate their status; (w) responsive to the response in step (v) indicating the user wishes to change their status, receiving a response from the user; (x) responsive to the response in step (u) indicating the user wishes to change their status, changing the status of the user to match the response received in step (w). 